Meta schema is the evolution of type_descriptions.yaml, and holds all types of details that don't fit neatly into the JSON schema.

Initial use cases include:

• Property descriptions. Previously done via type_descriptions.yaml, we should evolve this to more precisely model the semantics. I.e. break out high level description, SDK interpretation, default behavior.
• SDK extension plugin interfaces. Tracking which types can reference SDK extension plugin interfaces via the ComponentProvider mechanism.
• SDK implementation status. Track which types and properties are supported by which SDK implementations. Update I've sketched this out on a separate branch here (see generated markdown here). Will open a followup PR to keep things slightly more reviewable.

I wrote a useful summary of the meta schema and associated tasks here: https://github.com/jack-berg/opentelemetry-configuration/blob/meta-schema/CONTRIBUTING.md#meta-schema

Please read while reviewing!